.PN Registry Policies
This document sets out the policies that cover the operation of the .pn domain registry which consists of the .pn, .co.pn, .net.pn, org.pn, edu.pn & gov.pn DNS zones. In agreeing to the .PN Registry-Registrar Agreement (“RRA”), Registrars and Registrants agree to adhere to the policies set out in this document:
- .PN Registry-Registrar Lifecycle Policy
- .PN Registrar Eligibility Policy
- .PN Add Grace Period Limit Policy
- .PN Contact Data Policy
- .PN Inter-Registrar Transfer Policy
- .PN Registration Policy
- .PN Registry Domain Pricing Policy
- .PN Reseller Policy
- .PN Dispute Policy
- .PN Domain Name Abuse Policy
- .PN Registrant Terms and Conditions
- .PN Definitions Used in Policies
.PN Registry-Registrar Lifecycle Policy
Policy version: 1.0 – 01-2025
1. Registry-Registrar Lifecycle
1.1 The Registry operates a lifecycle with Registry Grace Periods as follows:
| Grace Period | Settings |
| Add Grace Period (subject to add grace period limits policy) | 5 days |
| Renew Grace Period | 5 days |
| Transfer Grace Period | 5 days |
| Auto-renew Grace Period | 45 days |
| Redemption Grace Period | 30 days |
| Pending Delete Grace Period | 5 days |
1.2 Transfer Lock on registration, transfer or change of registrant
A. The registry will not apply a transfer lock on registration, transfer or change of registrant.
B. Registrars may and are encouraged to utilise transfer locks as a matter of good security practice but where they do so must remove them at the Registrant’s request in accordance with the registry’s Inter-Registrar Transfer Policy.
2. Notice to Registrants of Fees and Procedures
2.1 Registrars must make their renewal fees reasonably available to Registrants and prospective Registrants at the time of registration of a domain.
A. At a minimum, these fees must be clearly displayed on the Registrar’s website and a link to these fees must be included in the Registrar’s registration agreements. Registrars who do not offer or provide Registrar services through a website must at least include the fees in their registration agreements.
B. Additionally, Registrars must ensure that these fees are displayed on their resellers’ websites.
3. Domain Cancellation
3.1 If a Registrant wishes to cancel their domain, they may do so at any time subject to Registry policies.
A. To cancel a domain, a Registrant must do so via their Registrar, requesting the deletion of their domain.
3.2 Registrars must:
A. Reject cancellation requests for any domains with a ‘server delete prohibited’ lock.
B. Process properly authorised domain cancellation requests from a registrant within five (5) days by requesting the Registry to ‘delete’ the domain.
3.3 The Registry will:
A. Provided a domain is not subject to a delete prohibition, place a deleted domain into the Redemption Period.
B. If the domain is not restored within the Redemption Period, put the domain into a Pending Delete Grace Period.
C. At the end of the Pending Delete Grace Period purge the domain from the Registry.
4. Expiration Reminder Notices
4.1 Registrars are required to notify Registrants of their expiry date at least as follows:
A. Approximately one month prior to expiry.
B. Approximately one week prior to expiry.
C. If not renewed by the Registrant with the Registrar before expiry at or within 5 days after expiry.
D. If a change of Registrant occurs at or after one month before expiry the new Registrant must be notified of the expiry date.
4.2 Registrars must describe the methods used to deliver pre- and post-expiration reminder notifications to Registrants.
A. If a Registrar offers registration and renewal via a website the information must be displayed there.
B. This description should generally include communications channels/media that will be used and identification of the point of contact to which the notices will be transmitted (e.g. email to Registrant, telephone call to administrative contact, postal mail to customer, etc…).
C. Registrars’ registration agreements must include either a similar description of its notification methods or a link to the applicable page(s) on its website where this information is available.
D. Additionally, Registrars must ensure that these communication methods are described on their resellers’ websites.
5. Renewals
5.1 A Registrar must not renew a domain without the explicit consent of a Registrant. A Registrar is offered by the Registry the benefit of the Auto-renew Grace Period to receive that consent.
5.2 Failure by the Registrant to consent to the renewal of a domain, shall in the absence of extenuating circumstances, result in the deletion of the domain by the end of the Auto-renew Grace Period by the Registrar (although the Registrar may choose to delete the name earlier).
5.3 Extenuating circumstances are defined as:
A. Dispute service action.
B. Valid court order.
C. Failure of a Registrar’s renewal process (which does not include failure of a Registrant to respond).
D. The domain is used by a nameserver that provides DNS service to third-parties (additional time may be required to migrate the records managed by the nameserver).
E. The Registrant is subject to bankruptcy proceedings, payment dispute (where a Registrant claims to have paid for a renewal, or a discrepancy in the amount paid), billing dispute (where a Registrant disputes the amount on a bill).
F. The domain is subject to litigation in a court of competent jurisdiction.
G. Other circumstance as approved specifically by the Registry Operator.
5.4 Where the Registrar chooses, under extenuating circumstances, to renew a domain without the explicit consent of the Registrant, the Registrar must maintain a record of the extenuating circumstances associated with renewing that specific domain for inspection by the Registry Operator.
5.5 In the absence of consent to renew by the Registrant or extenuating circumstances, a Registrar must request deletion of a domain within the Auto-renew Grace Period.
5.6 Failure by the Registrar to delete the domain within the Auto-renew Grace Period will result in the domain being renewed for a 1-year period.
5.7 Registrars are not required by Registry policy to interrupt the DNS resolution path during the Auto-renew Grace Period of an expired domain. However, if the Registrar directs web traffic to the domain to a web page while the domain is still renewable by the Registrant, that web page must conspicuously indicate that the domain is expired and provide renewal instructions.
5.8 Registrars shall provide notice to each new Registrant describing the details of their deletion and auto-renewal policy including the expected time at which a non-renewed domain would be deleted relative to the domains expiration date, or a date range not to exceed ten (10) days in length. If a Registrar makes any material changes to its deletion policy during the period of the registration agreement, it must make at least the same effort to inform the Registrant of the changes as it would to inform the Registrant of other material changes to the registration agreement.
5.9 If the Registrar operates a website for domain registration or renewal, details of the Registrar’s deletion and auto-renewal policies must be clearly displayed on the website.
5.10 Beginning at the time of expiration and through to the end of the Redemption Grace Period the Registrant at the time of expiration must be permitted by the Registrar to renew the expired domain.
6. Renew Grace Period
6.1 Only one Renew Grace Period can apply to a domain.
6.2 Domains in Renew Grace Period can be renewed but in doing so confirms the acceptance of the early end of any existing Renew Grace Period.
7. Redemption Grace Period
7.1 The Registry offers a Redemption Grace Period immediately following the deletion request of a domain, during which time the deleted domain may be restored at the request of the Registrant by the Registrar that deleted it. Domains deleted during the Registry Add Grace Period are not subject to the Redemption Grace Period.
7.2 During the Redemption Grace Period, the Registry disables DNS resolution and prohibits updates. The Registry will also clearly indicate in its Registration Data Directory Service result for the domain that it is in its Redemption Grace Period.
7.3 Registrars must permit the Registrant to restore a deleted domain during Redemption Grace Period for no additional charge other than any outstanding renewal fees.
7.4 Registrars must not restore domain to assume rights, use or sell the domain for themselves or a third-party that is not the Registrant.
8. Impact of Disputes
8.1 In the event that a domain which is the subject of a Registration dispute is deleted or expires during the course of the Registration dispute, the complainant in the dispute will have the option to renew or restore the domain under the same commercial terms as the Registrant. If the complainant renews or restores the domain, the domain will be placed in clientHold and clientTransferProhibited status, the RDDS contact information for the Registrant will be removed, and the RDDS contact entry will indicate that the domain is subject to dispute. If the complaint is terminated, or the dispute finds against the complainant, the domain must be deleted within 45 days. The Registrant retains the right under the existing Redemption Grace Period provisions to recover the domain at any time during the Redemption Grace Period and retains the right to renew the domain before it is deleted.
.PN Registrar Eligibility Policy
Policy version 1.0 – 01-2025
1. Accredited Registrar
1.1 To be a .PN accredited Registrar you must:
A. Be and remain whilst accredited:
i. A public body of Pitcairn, Henderson, Ducie and Oeno Islands; or
ii. An ICANN accredited Registrar under the 2013 ICANN Registrar Accreditation Agreement (as updated from time-to-time by ICANN); or
iii. A legal entity, not a natural person, who has:
1. Placed a deposit of at least USD 20,000 on account; or
2. More than 200 domains under management in the .PN top-level domain.
B. Enter into the Registry-Registrar Agreement for .PN with the Registry.
1.2 If, once accredited, you cease to meet the eligibility criteria set out in the current Registrar Eligibility Policy, you must notify the Registry Operator with details including any expected steps to rectify the matter.
1.3 Only one (1) Registrar accreditation for the .PN Registry is allowed per legal entity.
.PN Add Grace Period Limits Policy
Policy version 1.0 – 01-2025
1. Add Grace Period
1.1 The Add Grace Period (“AGP”) shall be restricted as:
A. During any given month, the Registry Operator shall not offer any refund to a Registrar for any domains deleted during the AGP that exceed:
i. 10% of that Registrar’s net new registrations (calculated as the total number of net adds of one-year through ten-year registrations, or
ii. Fifty (50) domains, whichever is greater, unless an exemption has been granted by the Registry Operator.
1.2 A Registrar may seek an exemption from the Registry Operator from the application of such restrictions in a specific month, upon the documented showing of:
A. Extraordinary circumstances:
i. For any Registrar requesting such an exemption, the Registrar must confirm in writing to the Registry Operator how, at the time the domains were deleted, these extraordinary circumstances were not known, reasonably could not have been known, and were outside the Registrar’s control. Acceptance of any exemption will be at the sole and reasonable discretion of the Registry Operator, however “extraordinary circumstances” which reoccur regularly for the same Registrar will not be deemed extraordinary.
B. Evidence the domain(s) were being used to commit DNS Abuse or were fraudulent registrations:
i. For any Registrar requesting such an exemption, the Registrar must confirm in writing to the Registry Operator full details of the DNS abuse or fraudulent registrations. Acceptance of any exemption will be at the sole and reasonable discretion of the Registry Operator.
.PN Contact Data Policy
Policy version 1.0 – 01-2025
1. Contact Information
1.1 A Registrant must supply contact information to the Registrar at the time of registration and it must be updated as and when the contact data changes. Registrants are responsible for ensuring all contact data remains accurate.
1.2 A Registrar must supply the Registrant’s contact information to the Registry at the time of registration and it must be updated as and when the contact data changes.
1.3 There are four types of contacts stored in the Registry. The table below indicates the information that Registrars must enter for each contact object.
| Contact Type | Status | Requirement on Registrar |
| Registrant | Mandatory | This contact will be recognised as the beneficial user who is legally responsible for the domain in contract to the Registry Operator and must be provided by the Registrar to the Registry Operator. |
| Administrative | Optional | If the Registrant wishes this data to be available to the Registry and/or published on the Registration Data Directory Service, it can be provided but is not required. |
| Technical | Optional | |
| Billing | Optional |
1.4 The sole purpose of the Contacts is to provide legal and/or role specific contact details for the Registrant to the Registry and/or third parties for legitimate purposes (e.g. if a Registrar ceases trading and domains need to be moved to an alternative Registrar, or legitimate legally valid requests for disclosure, etc.).
1.5 Registrars and/or Resellers and/or Registrants must not:
A. Use the Contact fields for any purpose other than as set out in paragraph 1.3. (e.g. “This domain is for sale”).
B. Do anything which may have the effect of concealing the true identity of the Registrant from the Registry Operator unless specifically permitted otherwise by another published Registry policy.
1.6 Each contact is made up of the following information:
| Field | Description | |
| If an individual | If an organisation | |
| Name | Contact legal name. | Contact legal name or role within organisation. |
| Organisation | Not applicable. | The legal name of the organisation. |
| Address | A full postal address for the contact. | |
| Telephone | A phone number including country code for the contact. | |
| Fax | Optional | |
| An email address for the contact. | ||
| Disclosure fields | The contact may opt to set disclosure information to allow the publication of data on the Registry Data Directory Service. Each of the fields above have discreet disclosure settings. | |
2. Maintenance of Contact Information
2.1 Failure to notify changes to contact or other information may result in the suspension or deletion of the Registrant’s domain.
2.2 Registrars must update Registrant data in the Registry within five (5) business days of receiving the updated information from the Registrant.
2.3 At least annually, a Registrar must present to the Registrant the current domain contact information and remind the Registrant that the provision of inaccurate contact data can be grounds for suspension or deletion of their domain. Registrants must review their domain contact information and make any corrections.
2.4 When a Registrar restores a domain (from the Redemption Grace Period) that had been deleted on the basis of submission of false contact data or non-response to Registrar inquiries, the domain must be placed on clientHold status until such time that the Registrant has provided updated and accurate contact information.
2.5 Change of Registrant vs updates to contact details:
A. Updates to a single contact object will be recognised as corrections to existing contact data for an existing legal entity.
B. To change the legal entity that is the Registrant of a domain, a new contact object should be created with the new Registrants’ details and the domain updated to utilise the new contact object.
3. Prohibition of Privacy and Proxy Services
3.1 Registrars, Reseller and Registrants are forbidden from providing privacy and/or proxy services for domain contact information to the Registry.
.PN Inter-Registrar Transfer Policy
Policy version 1.0 – 01-2025
1. Inter-Registrar Transfer Process
1.1 This document sets out the Inter-Registrar transfer policy for the .pn Country Code Top-Level Domain (ccTLD).
1.2 It is a fundamental policy principle for the Registry that Registrants may choose from a competitive Registrar market to register or maintain their domains and must be able to move between Registrars accordingly.
2. Registrant Request
2.1 In order to transfer a domain between Registrars a Registrant must ask the losing Registrar to:
A. Set and provide them with a Transfer Authorisation Code. Any request to set a new Transfer Authorisation Code will also be considered to be a request to expire any existing Transfer Authorisation Codes.
B. Remove any Registrar set transfer locks on their domain before requesting the gaining Registrar to transfer the domain.
3. Losing Registrar
3.1 When asked to transfer a domain, the losing Registrar must:
A. Ensure authenticity of the request from their Registrant.
B. Remove any transfer locks that the Registrar has set on the domain at no charge when asked to do so by the Registrant. Unless the Registrar can show the lock is in place to deal with an attempt to genuinely prevent domain name abuse and/or adherence to other Registry policies.
C. For the avoidance of doubt, a Registrar imposing a transfer lock without consent of the Registrant after the create, update or transfer in of a domain or its associated objects where there is no other evidence of domain name abuse or breach of policy is not allowed. Consent may be provided within a registrar’s terms and conditions, but any terms may not restrict the registrants right to removal of the lock in accordance with registry policy.
D. Set a Transfer Authorisation Code at the Registry for the domain.
E. Provide the Transfer Authorisation Code to the Registrant within five (5) days at no charge.
F. Retain records, which must be made available to the Registry Operator’s compliance team in a transfer dispute or audit of compliance, pertaining to the provision of the Transfer Authorisation Code for 15 months including:
i. Timestamp of Transfer Authorisation Code being set.
ii. Communication method of the Transfer Authorisation Code.
iii. Who the Transfer Authorisation Code was provided to.
4. The Registrant
4.1 The Registrant must:
A. Agree to the gaining Registrars’ terms and conditions of service including binding to current Registry policies and Registrants Terms and Conditions.
B. Request the transfer of the domain by providing a valid Transfer Authorisation Code to the gaining Registrar.
4.2 The Registrant may:
A. Request configuration changes for the domain to be put in place post-transfer.
B. Renew the domain for a minimum of one (1) year except where that would result in an expiry date more than 10 years in the future.
C. Transfer without renewal, provided the gaining registrar supports incoming transfers without renewal, except if the domain is in the Auto-renew Grace Period.
5. The Gaining Registrar
5.1 The gaining Registrar must:
A. Bind the Registrant to their terms and conditions and the Registry policies and Registrant Terms and Conditions and be able demonstrate this to the Registry Operator’s compliance team.
B. Submit a transfer request to the Registry:
i. Including the Transfer Authorisation Code.
ii. Only request a renewal with transfer if the Registrant has requested the renewal period. For the avoidance of doubt registrars are free to charge for incoming transfers whether a renewal is requested or not.
iii. If the domain is in the Auto-renew Grace Period, the Registrar must request a minimum of one (1) year renewal for the transfer to be accepted.
6. The Registry
6.1 The Registry will immediately upon receipt of a transfer request verify that:
A. No locks exist on the domain to prevent transfer.
B. The Transfer Authorisation Code for the domain is valid.
6.2 Provided the verification in preceding step is ok, the domain will be moved immediately to the new Registrar:
A. If the Registrar did not request renewal, the domain will transfer with no charge from the Registry to the Registrar.
B. If the Registrar requested a renewal, the appropriate renewal term will be processed as part of the transfer.
C. If the domain is in the Auto-renew Grace Period, the auto renewal will be cancelled resulting in only the renewal requested as part of the transfer request being charged.
7. Complaints Regarding Inter-Registrar Transfers
7.1 A complaint may be made to the Registry by a Registrant against the losing Registrar if:
A. The losing Registrar fails to remove a transfer lock and/or provide a Transfer Authorisation Code to a Registrant in accordance with this policy.
B. The losing Registrar does not take reasonable steps to ensure the authenticity of a request to provide a Transfer Authorisation Code; and/or provides the Transfer Authorisation Code to an unauthorised third party.
7.2 A complaint may be made by the losing Registrar to the Registry as to the legitimacy of an inter-Registrar transfer.
A. The losing Registrar may dispute an inter-Registrar transfer which has completed on behalf of, and with the consent of, the Registrant by raising a complaint with the Registry.
7.3 The outcome of an investigation into any complaint under this policy may result in the Registry:
A. Upholding the status quo.
B. Putting a domain into the state the Registrant intended.
C. Suspending a Registrar for breach of policy.
D. Terminating a Registrar’s Registry-Registrar Agreement for breach of policy.
.PN Registration Policy
Policy version 1.0 – 01-2025
1. Registration
1.1 Domain names are registered on a first-come, first-served basis.
1.2 Domains can be registered in:
A. .pn
B. co.pn – this zone is recommended for, but not limited to, commercial organisations.
C. org.pn – this zone is recommended for, but not limited to, non-commercial organisations.
D. net.pn – this zone is recommended for, but not limited to, network providers.
1.3 Only Pitcairn Islands Administration can register domains in gov.pn and edu.pn.
1.4 To register a domain in any .pn zone, the Registrant must agree to terms and conditions of registration.
1.5 In order to register a domain, a Registrant must select an accredited Registrar who meet the conditions set in the ‘Registrar Eligibility Policy’.
1.6 If in the Pitcairn Islands Administration unfettered opinion, a domain is unsuitable for operation in the .pn top level domain for any reason then it may require the Registry Operator to do one or more of the following:
A. Prohibit new registration of the domain.
B. Prohibit renewal of an already registered domain.
C. Prohibit operation of an already registered domain on the internet.
.PN Registry Domain Pricing Policy
Policy version 1.0 – 01-2025
1. Domain Pricing
1.1 Domain names within the top-level domain will be classified either as:
A. Standard priced domains.
B. Non-standard priced domains.
1.2 Standard priced domains:
A. The .pn zone will be charged at USD 100 per annual increment of expiry date.
B. The co.pn, .net.pn and org.pn zones will be charged at USD 50 per annual increment of expiry date.
1.3 Non-standard priced domains:
A. Will be individually priced in the Registry, the price of registering and/or renewing these domains will be available from the Registry system.
B. Required for operation by the Pitcairn Islands Administration will be charged at USD 0 per annual increment.
1.4 Restoring a domain from a Registry redemption period will be charged at USD 0 in addition to any renewal fees.
1.5 A domain cannot be extended to have an expiry date more than 10 years in the future.
2. Registry Lock
2.1 The Registry lock service shall be charged monthly at USD 8.33 per domain, host or contact object.
.PN Reseller Policy
Policy version 1.0 – 01-2025
1. Reseller
1.1 Registrars are not prohibited from dealing with Registrants indirectly (for example, through ‘Resellers’) but:
A. Registrar’s may not transfer, subcontract or delegate any of their rights or obligations under the Registry-Registrar Agreement or Registry Policies.
B. As between Registrar and Registry, Registrars are responsible for the Registrant and the information, service, marketing and advice they are given, whether or not the Registrar actually deal with them directly.
C. The Registry is not required to deal with or give any recognition or special privilege to any Registrar’s Resellers.
D. Any actions by a Registrar’s Resellers may have a direct impact on that Registrar’s compliance and will be treated as actions by the Registrar for the purposes of compliance with both Registry Registrar Agreement and Registry Policy.
E. Registrar’s must make their Resellers aware of the Registry’s policies and Registrar Accreditation Agreement terms, available from our website, and ensure that the way that they deal with Registrants is compatible with those policies and terms.
F. A Registrar’s contract with their Reseller must be compatible with the terms of the Registry-Registrar Agreement and Registry Policies. If requested, a Registrar must provide the Registry with copies of their contracts with their Resellers, or relevant excerpts that relate to our domain registrations or the issue at hand.
G. It is a Registrar’s responsibility to ensure that information given to their Resellers, which is relevant to the domain entry, is provided to the Registrar and that the Registry is updated accordingly. For example, where we oblige the Registrar to do something because the Registrar becomes aware of a change in Registrant’s information or situation, this also applies to a situation where the Registrar’s Reseller has become aware of a change in Registrant’s information or situation.
H. On request a Registrar must confirm to the Registry whether a person or organisation is a Reseller and provide the Registry with full contact details for them.
.PN Dispute Policy
Policy version 1.0 – 01-2025
1. Disputes
1.1 For the .pn Country Code Top-Level Domain the Registry Operator has adopted the Uniform Domain Name Dispute Resolution Policy (UDRP) established by ICANN for trademark related disputes. The World Intellectual Property Organization (WIPO) is the ICANN-approved service provider selected for administering disputes relating to .pn domains.
1.2 Registrars must abide by the UDRP policy as set out by ICANN (and as updated from time-to-time by ICANN). https://www.icann.org/resources/pages/policy-2024-02-21-en.
.PN Domain Name Abuse Policy
Policy version 1.1 – 06-2025
1. Registry Operator
1.1 The Registry Operator is committed to ensuring that the Internet is a force for good. To ensure that domains in the top level domain (the “TLD”) are registered and used in accordance with that goal, all domains registered in the TLD and Accredited Registrars must comply with this policy.
1.2 The Registry Operator reserves the right, at its sole discretion, at any time and without limitation to deny, cancel, suspend, redirect or transfer any domain or transaction, or place any domain on registry lock, hold or similar status as it deems necessary for any of the following reasons:
A. To protect the integrity and stability of the Registry for the TLD, or other Registries;
B. To comply with any applicable laws, government rules or requirements, requests of law enforcement, or any dispute resolution process;
C. To avoid any liability, civil or criminal, on the part of the Registry Operator, as well as its affiliates, subsidiaries, officers, directors, and employees;
D. As per the terms of any applicable registration agreement, or the Registry-Registrar Agreement for the TLD;
E. To correct mistakes made by the Registry Operator or any Registrar in connection with a domain registration;
F. As needed during the resolution of a dispute;
G. Where the Registrant has failed to provide accurate, correct and up to date contact information, including names, addresses, phone numbers and email addresses;
H. Where a domain is being used, or has a high risk of being used, for illegal, disruptive, malicious, or fraudulent action, including, without limitation for the purposes of: DNS Abuse; distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law;
I. Where the domain is being used for an unlawful purpose;
J. Where the domain would, on the face of it, tend to indicate, comprise or promote a sexual offence.
1.3 The Registry Operator will promptly report to the Pitcairn Islands Administration any domain which falls within 1.2 (h) – (j) inclusive, and co-operate with any law enforcement requests.
1.4 The Registry Operator shall publish on its website its accurate contact details including a valid email address or webform and mailing address as well as a primary contact for handling reports related to malicious conduct in the TLD, including DNS Abuse. Upon receipt of such reports, the Registry Operator shall provide the reporter with confirmation that it has received the report.
1.5 Where the Registry Operator reasonably determines, based on actionable evidence, that a registered domain in the TLD is being used for DNS Abuse, the Registry Operator will promptly take the appropriate mitigation action(s) that are reasonably necessary to contribute to stopping, or otherwise disrupting, the domain from being used for DNS Abuse. Such action(s) shall, at a minimum, include: (i) the referral of the domains being used for the DNS Abuse, along with relevant evidence, to the sponsoring Registrar; or (ii) the taking of direct action, by the Registry Operator, where the Registry Operator deems appropriate. Action(s) may vary depending on the circumstances of each case, taking into account the severity of the harm from the DNS Abuse and the possibility of associated collateral damage.
1.6 Registry Operator shall take action to remove orphan glue records (as defined at https://www.icann.org/en/committees/security/sac048.pdf ) when provided with evidence in written form that such records are present.
.PN Registrant Terms and Conditions
Policy version 1.0 – 01-2025
1. Registrant Terms and Conditions
1.1 Registrars act as agents of the Registrant in instructing the Registry to register, maintain and delete domain names. As a Registrant’s agent a Registrar must ensure registrants agree to these terms and conditions.
1.2 The following terms set out the contract between the Registrant and the Registry Operator:
A. The Registrant shall provide to the Registrar accurate and reliable contact details and correct and update them within seven (7) days of any change during the term of the domain registration, including: the full name, postal address, email address, voice telephone number of the Registrant; name of authorized person for contact purposes and organisation name in the case of a Registrant that is an organization, association, or corporation.
B. A Registrant’s wilful provision of inaccurate or unreliable information, its wilful failure to update information provided to the Registrar within seven (7) days of any change, or its failure to respond for over fifteen (15) days to inquiries by the Registrar concerning the accuracy of contact details associated with the Registrant’s domain shall constitute a material breach of the Registrant-Registrar contract and be a basis for suspension and/or cancellation of the domain.
C. Any Registrant that intends to license use of a domain to a third-party is nonetheless the Registrant of record and is responsible for providing its own full contact information and for providing and updating accurate technical and administrative contact information adequate to facilitate timely resolution of any problems that arise in connection with the domain. A Registrant licensing use of a domain according to this provision shall accept liability for harm caused by wrongful use of the domain, unless it discloses the current contact information provided by the licensee and the identity of the licensee within seven (7) days to a party providing the Registrant reasonable evidence of actionable harm.
D. The Registrant shall consent to the data processing by the Registrar and Registry required to maintain the domain Registry including that required to detect or prevent malicious activity.
E. The Registrant shall represent that notice has been provided to any third-party individuals whose Personal Data are supplied to the Registrar by the Registrant, and that the Registrant has obtained consent for the Registrar and Registry Operator to process that data.
F. The Registrant shall represent that, to the best of the Registrant’s knowledge and belief, neither the registration of the domain nor the way it is directly or indirectly used infringes the legal rights of any third-party.
G. The Registrant must not utilise the domain for any illegal purpose.
H. For the adjudication of disputes concerning or arising from use of the domain, the Registrant shall submit, without prejudice to other potentially applicable jurisdictions, to the jurisdiction of the courts in either:
i. The Registrant’s domicile
ii. Where the Registrar is located
iii. Where the Registry Operator is located
iiii. The Pitcairn, Henderson, Ducie and Oeno Islands.
I. The Registrant shall agree that its registration of the domain shall be subject to suspension, cancellation, or transfer pursuant to any Registry Policy, or pursuant to any Registrar or Registry procedure not inconsistent with any Registry Policy, (1) to correct mistakes by the Registrar or the Registry Operator in registering the name or (2) for the resolution of disputes concerning the domain.
J. The Registrant shall indemnify and hold harmless the Registry Operator and its directors, officers, employees, and agents from and against any and all claims, damages, liabilities, costs, and expenses (including reasonable legal fees and expenses) arising out of or related to the Registrant’s domain registration.
.PN Definitions Used in Policies
Policy version 1.0 – 01-2025
1. Definitions
1.1 The following terms are used in the policy for .PN:
A. “Registrant” means a legal entity who has entered into a legal agreement to register a domain in the Registry.
B. “Registrar” means a legal entity that has entered into a Registry-Registrar Agreement with the Registry Operator for the domain.
C. “Registration Data Directory Service” or “RDDS” means a Registry service which allows users to query the content of the Registry database.
D. “Registry Operator” means Nominet operating under contract and oversight of the ccTLD Manager for the provision of services in the domain.
E. “Registry-Registrar Agreement” or “RRA” means the legally binding contract for access to the Registry.
F. “Registry” means the operational systems that run the domain.
Minerva House, Edmund Halley Road, Oxford Science Park, OX4 4DQ, United Kingdom